Apparatus and methods for enhanced paging in wireless networks

ABSTRACT

Apparatus and methods for managed or “intelligent” paging of a user device in one or more wireless networks. In one embodiment, the apparatus and methods provide enhanced wireless services which enable prioritized paging operations of a given user device (e.g., a mobile 3GPP-compliant UE) within two or more mobile networks (e.g., PLMNs) when the UE is operating in a “dual” mode such as 3GPP 5G NR dual-SIM, dual standby (DSDS) mode. In one implementation, the UE contains multiple SIM cards to enable connection to different PLMNs simultaneously, such that paging associated with one network can be managed and prioritized as needed when the UE is actively utilizing another network.

PRIORITY

This application is a continuation of and claims priority to co-ownedand U.S. patent application Ser. No. 16/879,345 filed on May 20, 2020entitled “APPARATUS AND METHODS FOR ENHANCED PAGING IN WIRELESSNETWORKS,” and issuing as U.S. Pat. No. 11,057,865 on Jul. 6, 2021,which is incorporated herein by reference in its entirety.

COPYRIGHT

A portion of the disclosure of this patent document contains materialthat is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure, as it appears in the Patent and TrademarkOffice patent files or records, but otherwise reserves all copyrightrights whatsoever.

BACKGROUND 1. Technological Field

The present disclosure relates generally to the field of wirelessdevices and networks thereof, and specifically in one exemplary aspectto “intelligent” and adaptive paging notification to user devices suchas wireless-enabled smartphones or other communication devices.

2. Description of Related Technology

A multitude of wireless networking technologies, also known as RadioAccess Technologies (“RATs”), provide the underlying means of connectionfor radio-based communication networks to user devices. Such RATs oftenutilize licensed radio frequency spectrum (i.e., that allocated by theFCC per the Table of Frequency Allocations as codified at Section 2.106of the Commission's Rules). Currently only frequency bands between 9 kHzand 275 GHz have been allocated (i.e., designated for use by one or moreterrestrial or space radio communication services or the radio astronomyservice under specified conditions). For example, a typical cellularservice provider might utilize spectrum for so-called “3G” (thirdgeneration) and “4G” (fourth generation) wireless communications asshown in Table 1 below:

TABLE 1 Technology Bands 3G 850 MHz Cellular, Band 5 (GSM/GPRS/EDGE).1900 MHz PCS, Band 2 (GSM/GPRS/EDGE). 850 MHz Cellular, Band 5(UMTS/HSPA+ up to 21 Mbit/s). 1900 MHz PCS, Band 2 (UMTS/HSPA+ up to 21Mbit/s). 4G 700 MHz Lower B/C, Band 12/17 (LTE). 850 MHz Cellular, Band5 (LTE). 1700/2100 MHz AWS, Band 4 (LTE). 1900 MHz PCS, Band 2 (LTE).2300 MHz WCS, Band 30 (LTE).

User client devices (e.g., smartphone, tablet, phablet, laptop,smartwatch, or other wireless-enabled devices, mobile or otherwise)generally support multiple RATs that enable the devices to connect toone another, or to networks (e.g., the Internet, intranets, orextranets), often including RATs associated with both licensed andunlicensed spectrum. In particular, wireless access to other networks byclient devices is made possible by wireless technologies that utilizenetworked hardware, such as a wireless access point (“WAP” or “AP”),small cells, femtocells, or cellular towers, serviced by a backend orbackhaul portion of service provider network (e.g., a cable network). Auser may generally access the network at a node or “hotspot,” a physicallocation at which the user may obtain access by connecting to modems,routers, APs, small cells, etc. that are within wireless range.

5G New Radio (NR) and NG-RAN (Next Generation Radio Area Network)

NG-RAN or “NextGen RAN (Radio Area Network)” is part of the 3GPP “5G”next generation radio system. 3GPP has specified Release 16 NG-RAN (andis currently working on Release 17), its components, and interactionsamong the involved nodes including so-called “gNBs” (next generationNode B's or eNBs). NG-RAN will provide high-bandwidth, low-latencywireless communication and efficiently utilize, depending onapplication, both licensed and unlicensed spectrum of the type describedsupra in a wide variety of deployment scenarios, including indoor “spot”use, urban “macro” (large cell) coverage, rural coverage, use invehicles, and “smart” grids and structures. NG-RAN will also integratewith 4G/4.5G systems and infrastructure, and moreover new LTE entitiesare used (e.g., an “evolved” LTE eNB or “eLTE eNB” which supportsconnectivity to both the EPC (Evolved Packet Core) and the NR “NGC”(Next Generation Core, also called “5GC”).

As background, FIG. 1 shows the 5G architecture 100 and componentsthereof as defined in 3GPP TS 23.501 (FIG. 4.2.3-1 thereof).

FIG. 2A shows the 5G system architecture in the non-roaming case,illustrating how various network functions interact with each other.

FIG. 2B shows the 3GPP 5G architecture 230 for a UE connecting with andconcurrently accessing two networks (e.g., local and central) usingmultiple PDU sessions. As shown, two Session Management Functions (SMF)are selected for supporting two different Packet Data Unit (PDU)sessions via two separate UPFs (User Plane Functions). The 3GPP 5Garchitecture also supports concurrent access by a UE to two networks(e.g., local and central) within a single PDU session.

As further background, 3GPP has also defined roaming architecturesbetween two networks Home Public Land Mobile Network (HPLMN), andVisited Public Land Mobile Network (VPLMN) when the two PLMN haveoverlap in coverage area. FIG. 2C shows the architecture 250 for roamingbetween HPLMN 253 and VPLMN 255 as defined in 3GPP TS 23.501 (FIG.4.2.4-3 thereof), specifically the roaming architecture in the case ofhome routed scenario with serviced-bases interface within the ControlPlane. In this architecture, the UE is connected to the Data Network(DN) 307 from the HPLMN, and all traffic is routed from the HPLMN via aDN gateway (not shown).

FIG. 2D shows an architecture 270 similarly for roaming between HPLMNand VPLMN as defined in TS 23.501 (FIG. 4.2.4-1 thereof), specifically,the roaming architecture in the case of local breakout withservice-based interface within Control Plane. In this architecture, UEis connected to the DN 279 from the VPLMN, and the traffic istransported between the UE and the DN 279 without traversing a DNgateway (not shown) in the home network. Additionally, in thisarchitecture, the PCF 277 in VPLMN may interact with an ApplicationFunction (AF) 273 in order to generate Policy and Charging Control (PCC)rules.

In the extant 5G or 3GPP cellular wireless systems, when a UE connectswith another wireless Mobile Operating Network (MNO), the visitednetwork identifies the UE home network. If there is a roaming agreementbetween the home network and the visited network, the UE is able toconnect with the visited network.

As described in TS 23.503 (section 6.1.2.2.1), UE Route Selection Policy(URSP) information contains a list of prioritized Session Management(SM) policy rules, where each rule may have one or more TrafficDescriptor (TD) components associated with one or more route selectioncomponents. The UE uses these rules to determine if one or more TDs canbe associated to an established PDU session, can be offloaded to non3GPP access outside of a 3GPP session, or can trigger the establishmentof a new PDU session.

Paging in UE (e.g., Multi-SIM) Devices and Unaddressed Issues—

Multi-SIM devices (i.e., user devices with two or more subscriberidentity modules or SIMs, embodied as e.g., 3GPP UEs) are currentlydeployed commercially, and provide a solution for situations when the UEroams from its home network (e.g., an HPLMN), and intends to connect toa visited network (e.g., VPLMN) that does not have roaming agreementwith its home network. Each USIM provides a phone number and an identityfor the device in order the enable functions such receiving or makingcalls/texts/data on each number, including paging notifications fore.g., incoming data.

Extant 3GPP specifications do not specify particular implementation ofmulti-USIM UEs. Hence, each network operator and UE manufacturer mayimplement the Multi-USIM architecture and protocol differently,resulting in a variety of implementations and architectures.

As noted above, multi-USIM UEs are capable of connecting to multiplenetworks independently. One sub-species thereof, the Dual-USIM, alsoreferred to Dual-SIM Dual-Standby (DSDS) UEs are the most commoncommercially deployed multi-USIM devices. The Dual-USIM UEs are able toconnect to a first network using a first USIM (USIM-A), and to a secondnetwork using a second USIM (USIM-B) independent of the connectionmaintained by USIM-A. To reduce the manufacturing cost of such UEs, theradio and baseband components are often shared between the two USIMs.However, in such cases, coordination logic is needed to manage theoperation of two different USIMs, and to use the appropriate USIM withthe associated network with which it is registered. For instance, whilethe UE is connected to the first network associated with USIM-A, in thecycle between data transmissions for that network, the UE needs tomeasure the received signal from the second network associated withUSIM-B, monitor the paging channel, or read system information (e.g., SIblocks or SIBs) to, inter alia, maintain status of and determine thepossibility of connecting to the second network. The MUSIM UE in suchcases cannot “connect” to both networks simultaneously per se, butrather connects to one and maintains the other in a “standby” or idlestate for possible connection.

A multi-USIM UE (e.g., DSDS UE) assumes an operating environment whereinthe two networks associated with USIM-A and -B have an overlap in thecoverage area; hence, a data application within the UE can be allocatedto the appropriate network anytime when the UE is located in thecoverage area of that network. However, while the multi-USIM UE isactively communicating with one network (e.g., a PLMN associated toUSIM-A), the multi-USIM UE may receive network paging from the othernetworks (e.g., a PLMN associated to USIM-B). In the absence of anyprocedure for handing the paging requests from the other networks, themulti-USIM UE device may ignore the request, or autonomously leave theconnection with the current network in favor of the other network. Thissituation can present salient issues, however (e.g., unwantedinterruption, or failure to provide any notifications), and requiresspecial handling within the multi-USIM UE in order to provide good userexperience.

In currently proposed solutions, the Type of Service (ToS) Flow, whichis data included in the IPv4 packet header, specifies the data packetpriorities for such IP packets. IPv6 IP packets have a Traffic Class(TC) which can be used for similar purposes. Currently, both of thesefields (ToS and TC) are used for “Differentiated services” or“differentiated services code point (DSCP)” as stated by RFC 2474. Basedon the ToS/TC value, a packet can be placed in a prioritized queue ordismissed. As described in 3GPP TR 23.761, the ToS/TC value from the IPheader of the received IP packet, which identifies the correspondingQuality of Service (QoS), is mapped to a paging cause (PC) to besignaled to the UE.

The foregoing mechanism(s) raise particular issues with, inter alia,paging the UE. In particular, when a UE receives an IP packet fromdifferent applications (e.g., Skype, WhatsApp, etc.), the multi-USIM UEis not able to set the paging causes between different applications.Moreover, some applications may have higher priorities than thethen-current (e.g., in-focus) application which is transacting data, andthe multi-USIM UE requires that a paging cause be used to establishedthat relationship immediately. In such scenarios, the existing procedurethat maps e.g., ToS value to a paging cause, is not able to prioritizethe various paging causes. Hence, the multi-USIM UE may ignore an urgentpaging request, which can create unpleasant and undesirable userexperience, such as where the user does not receive an urgentnotification from a family member.

Accordingly, improved methods and apparatus are needed to enable, interalia, prioritizing paging requests originated from different networksfor a UE that can connect to the respective different networks (andpotentially different network operators), such as where one network isassociated with a first PLMN, and the second network is associated withanother PLMN. Specifically, such improved methods and apparatus wouldalso ideally allow a UE (such as e.g., multi-USIM UE) to prioritize thepaging requests based on the applications selections by the user andoperators. Such improved methods and apparatus would also allow the UEdistinguish between important downlink data and associated notificationsversus other unimportant data notifications, and further allow theprioritization scheme to “travel” with the user (e.g., be operative notonly within the user's home network, but also within a visited network(such as e.g., when the user travels away from home on business).

SUMMARY

The present disclosure addresses the foregoing needs by providing, interalia, methods and apparatus for providing enhanced multi-networkconnection and operation (including service/application pagingnotification support) for wireless mobile devices.

In a first aspect of the disclosure, computerized network apparatus foruse within a wireless network infrastructure is described. In oneembodiment, the apparatus includes: digital processing apparatus; atleast one data network interface in data communication with the digitalprocessing apparatus; and a storage device in data communication withthe digital processing apparatus, the storage device comprising astorage medium having at least one computer program.

In one variant, the at least one computer program is configured to, whenexecuted on the digital processing apparatus, cause the computerizednetwork apparatus to: receive first data relating to one or moreprocessing rules for respective one or more software applicationsoperative to execute on a user device; based at least on the receivedfirst data, determine at least one route selection policy associatedwith data traffic of the one or more software applications; and causeforwarding of second data relating to the at least one route selectionpolicy to the user device. In one implementation, the forwarding of thesecond data relating to the at least one route selection policy enablesthe user device to selectively implement the one or more processingrules for paging notifications sent to the user device when the userdevice is connected to the wireless network infrastructure.

In another variant, the second data includes data indicative of one ormore paging causes.

In a further variant, the at least one computer program is furtherconfigured to, when executed, enable selective routing of InternetProtocol (IP) packets to the user device, the IP packets associated withone of the software applications, the IP packets comprising adestination address associated with the particular one of the softwareapplications.

In another variant, the wireless network infrastructure is compliantwith 3GPP 5G NR (Fifth Generation New Radio) protocols, and the seconddata includes a URSP (UE Route Selection Policy). In one suchimplementation, the URSP (UE Route Selection Policy) includes at leastone Data Network Name (DNN) value.

In a further variant, the computerized network apparatus includes atleast: (i) a 5G NR Session Management Function (SMF), and (ii) a 5G NRUser Plane Function (UPF). In one implementation, the computerizednetwork apparatus further includes a Policy Control Function (PCF).

In another aspect, a method of performing paging notification managementwithin a wireless network is disclosed. In one embodiment, the methodincludes: receiving data indicative of user preferences fornotifications relating to each of a plurality of applications operativeto execute on a wireless computerized client device of the user; causinggeneration of one or more rules based on the received data; receiving aplurality of IP data packets at the wireless network, the plurality ofIP data packets generated by respective ones of data sources associatedwith each of the plurality of applications; processing the receivedplurality of IP data packets to map the IP data packets to a pluralityof paging causes; and causing transmission of at least one pagingnotification for each of the plurality of applications to the wirelesscomputerized client device, each of the at least one pagingnotifications comprising one of the plurality of paging causes.

In one variant, the method enables the wireless computerized clientdevice to selectively disposition each of the at least one pagingnotifications according to the user preferences.

In another variant, the method further includes assigning a plurality ofunique IP addresses to each of the plurality of applications, each ofthe plurality of IP data packets comprising an applicable one of theplurality of unique IP addresses. In one such implementation, thereceiving data indicative of user preferences for notifications relatingto each of a plurality of applications operative to execute on awireless computerized client device of the user includes receiving dataindicative of at least two groups, each of the groups comprising atleast one of the plurality of applications; and the method furtherincludes correlating each of the unique IP addresses to at least one ofthe plurality of paging causes.

In another aspect of the disclosure, a computerized mobile deviceconfigured for use within multiple mobile network environments isdescribed. In one embodiment, the device includes: digital processorapparatus; wireless interface apparatus in data communication with thedigital processor apparatus and configured for wireless communicationwith at least a first radio area network (RAN) utilizing a firstwireless access technology; and storage apparatus in data communicationwith the digital processor apparatus and comprising a storage medium,the storage medium comprising at least one computer program.

In one variant, the at least one computer program is configured to, whenexecuted on the digital processor apparatus: receive policy datarelating to data traffic management of a plurality of user applicationsoperative to execute on the computerized mobile device; receive aplurality of paging notifications from a first of the multiple mobilenetwork environments, the paging notifications each comprising a pagingcause which is differentiated relative to others of the plurality ofpaging notifications; and based at least on the received policy data andthe paging causes, selectively disposition each of the pagingnotifications.

In another variant, the selective disposition of at least one of thepaging notifications includes: terminating a connection with the firstnetwork environment; establishing a connection with a second of thenetwork environments; and requesting a PDU session be established viathe second network environment for receiving IP data traffic associatedwith one of the plurality of user applications.

In another variant, the computerized mobile device further includes:first subscriber identity apparatus configured to enable connection ofthe computerized mobile device to the first network environment; andsecond subscriber identity apparatus configured to enable connection ofthe computerized mobile device to the second network environment. In oneimplementation, the computerized mobile device includes a DSDS(dual-SIM, dual standby) device which is only capable of one networkconnection at a given time.

In another aspect, an enhanced client device is disclosed. In oneembodiment, the client device is a mobile device (e.g., smartphone ortablet) with DSDS and dual-SIM capability. In another embodiment, theclient device is configured as a CPE (consumer premises equipment) suchas a fixed wireless access (FWA) device mounted on a pole or rooftop orbuilding façade, and used to support other wireline or wireless premisesdevices such as WLAN APs/routers, or MSO set-top boxes.

In another aspect, a method for managing paging notifications from twoor more different wireless networks is disclosed. In one embodiment, themethod includes: evaluating applications and placing them in groupsbased on user preferences; reporting the application/groupsallocation(s) and their associated preferences to at least one of thenetworks; obtaining a set of rules; evaluating the set of rules toidentify the components of the rule matching a data unit based onselection criterion; associating the data unit to the matching rule; androuting the traffic on the data unit based on the prioritized list ofapplications in the groups.

In yet another embodiment, the method includes allocating a unique IPaddress to a user device for each group such that a paging cause can beassigned to an application using the group IP address. In one variant,the user device receiving the paging cause determines whether to respondor not, and how to respond (e.g., which network to utilize to receivedata associated with the page).

In another embodiment, the managing include grouping “important”applications into (1) “urgent” applications, wherein the user devicereceives paging notifications from the applications in this group anytime; (2) “default” applications, wherein the UE receives pagingnotifications from the applications in this group only when it is notengaged in communication with any other networks; and/or (3) “ignore fornow” applications, wherein the user device receives notifications fromthe applications in this group only when meeting certain criteria; e.g.,when the current time is within a certain time period.

In additional aspect of the disclosure, computer readable apparatus isdescribed. In one embodiment, the apparatus includes a storage mediumconfigured to store one or more computer programs, and includes aprogram memory or HDD or SSD on a computerized device such as a 5G NRnetwork entity (e.g., gNB) or UE device. In one variant, the one or morecomputer programs are configured to arbitrate access between two PLMNs(e.g., a 5G 3GPP PLMN and a non-3GPP PLMN).

In a further aspect of the disclosure, an enhanced 5G NR 3GPP UE (UEe)is disclosed. In one embodiment, the UEe includes: a receiver module, atransmitter module, and an application management module. In onevariant, the UEe may further include: a processor apparatus; a wirelessmodem chipset in data communication with processor apparatus; a programmemory in data communication with processor apparatus; a mass storage;and an RF front end module.

In further implementation, the program memory includes at least oneprogram which is configured to, when executed to the processorapparatus, causes to perform a grouping scheme for applications utilizedby the UEe based on their priority or importance to the user to beprocessed.

In another variant, the computerized mobile device further includessubscriber identity module logic in data communication with the dataprocessor apparatus, the subscriber identity module logic configured toprovide data enabling the establishment of the data communication withthe first network management entity as well as establishment of the datacommunication with the second network management entity. In oneimplementation, the subscriber identity module logic is part of a commonUniversal Subscriber Identity Module (USIM) having two discrete SIM datasets.

In another aspect of the disclosure, a network architecture isdisclosed. In one embodiment, the architecture includes enhancedentities configured to allow an enhanced UE to be aware of a differentnetworks' paging requests, including while connected to the othernetwork. In one variant, the architecture is applied within the samenetwork operator (e.g., MNO or MSO). In another variant, thearchitecture is applied within different network operator (e.g., twodifferent MNOs, two different MSOs, or between an MNO and MSO). In yetanother variant, the architecture is adapted for use in a networksharing model (e.g., wherein two or more entities share at leastportions of the infrastructure for their respective users or customers).

In another aspect of the disclosure, methods and apparatus enabling theuser device to be aware of network paging based on priorities ofapplications utilized by the user device are disclosed.

In one variant, a mobile device (e.g., DSDS-capable UE) belongs to afirst PLMN, while a second PLMN is used to provide additional(overlapping) network coverage.

In a further aspect of the disclosure, methods and apparatus for routingcategorized data traffic to a UE are described. In one embodiment, thecategorized data are associated to applications executed on the UE,which are categorized by the UE and the network such that a unique IPaddress is assigned to data packets in each category, allowing formapping of IP packets receiving from each category to a specific pagingcause, and consequently issuing the paging cause to the UE via pagingnotification(s).

In another aspect of the disclosure, network apparatus for use within awireless network is disclosed. In one embodiment, the network apparatusincludes an enhanced AF (Application Function) or AFe, and is configuredto at least recognize prescribed input related to prioritized or managedapplication processing from the enhanced UE (UEe) so as to enableestablishment of a managed paging awareness environment, includingsupport of a managed application paging and data processing model. Theapparatus may also generates enhanced URSP (UE Route SelectionsPolicies) or URSPe rules for UEes, thereby allowing the UEes to processoperative applications according to a prescribed management scheme.

In one variant, the network apparatus further includes an enhanced PCF(Policy Control Function) or PCFe process configured to at leastrecognize prescribed 3GPP 5G based network URSPe rules generated fromthe aforementioned AFe, and to inform the UEe of these URSPe rules andfunctions (including modifications thereto).

In another variant, the network apparatus includes an enhanced SMF(Session Management Function) SMFe process configured to map incomingdata IP addresses associated with individual UE applications to variousdesignated paging cause values.

In a further aspect, methods and apparatus for exerting operator controlover user device use of DNNs is disclosed.

In another aspect, methods and apparatus for conserving networkresources based on differentiated paging notification behavior isdisclosed.

In another aspect, an integrated circuit (IC) device implementing one ormore of the foregoing aspects is disclosed and described. In oneembodiment, the IC device is embodied as a SoC (system on Chip) device.In another embodiment, an ASIC (application specific IC) is used as thebasis of the device. In yet another embodiment, a chip set (i.e.,multiple ICs used in coordinated fashion) is disclosed. In yet anotherembodiment, the device comprises a multi-logic block FPGA device.

These and other aspects shall become apparent when considered in lightof the disclosure provided herein.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a functional block diagram of a prior art 5G systemarchitecture and the various components thereof.

FIG. 2A is a functional block diagram of a prior art 5G systemcomponents and interfaces thereof.

FIG. 2B is a functional block diagram of a prior art 5G systemarchitecture and the various component thereof configured for multiplePDU sessions.

FIG. 2C is a block diagram showing the prior art 5G home-routedarchitecture as defined in 3GPP TS 23.501 (FIG. 4.2.4-3 thereof).

FIG. 2D is a block diagram showing the prior art 5G local breakoutarchitecture as defined in 3GPP TS 23.501 (FIG. 4.2.4-1 thereof).

FIG. 3 is a block diagram showing a prior art approach for pagingnotification and data delivery to a UE within a 5G NR network.

FIG. 4 is a logical flow diagram illustrating one embodiment of ageneralized method of enhanced paging notification for a client deviceaccording to the present disclosure.

FIG. 4A is a logical flow diagram illustrating one implementation of thegeneralized method of FIG. 4 ; i.e., for paging notification of a DSDSmulti-USIM UEe with prioritized paging functionality according thepresent disclosure.

FIG. 4B is a tabular representation of an exemplary embodiment ofenhanced URSP rules implementing prioritized paging notification for amulti-USIM UE, according to the present disclosure.

FIG. 4C is a logical flow diagram illustrating another embodiment of ageneralized method of enhanced paging notification for a client deviceaccording to the present disclosure, wherein network-based processing isutilized.

FIG. 5 is a logical flow diagram illustrating one embodiment of a methodfor prioritizing of paging notifications of a multi-USIM UEe accordingthe present disclosure.

FIG. 6 is a logical flow diagram illustrating an embodiment of a methodnetwork operation with prioritized paging functionality according thepresent disclosure.

FIG. 6A is a logical flow diagram illustrating an exemplaryimplementation of the method of FIG. 6 .

FIG. 6B is a logical flow diagram illustrating another exemplaryimplementation of the method of FIG. 6 .

FIG. 7 is a block diagram of one embodiment of an enhanced 5G networkarchitecture according the present disclosure.

FIG. 7A is a ladder diagram illustrating paging notification message anddata flow according to one embodiment of the disclosure.

FIG. 8 a block diagram of one embodiment of an enhanced multi-network(i.e., HPLMN/VPLMN) roaming architecture according the presentdisclosure.

FIG. 9 is a functional block diagram illustrating an exemplaryembodiment of an enhanced PCF (PCFe) apparatus useful with variousembodiments of the present disclosure.

FIG. 10 is a functional block diagram illustrating an exemplaryembodiment of an enhanced SMF (SMFe) apparatus useful with variousembodiments of the present disclosure.

FIG. 11 is a functional block diagram illustrating an exemplaryembodiment of an enhanced AF (AFe) apparatus useful with variousembodiments of the present disclosure.

FIG. 12 is a functional block diagram illustrating an exemplaryembodiment of an enhanced 3GPP-compliant multi-USIM apparatus (UEe)useful with various embodiments of the present disclosure.

FIG. 13 is a functional block diagram of a first exemplary MSO networkarchitecture useful in conjunction with various principles describedherein.

FIG. 14 is a functional block diagram of an exemplary MNO networkarchitecture useful in conjunction with various principles describedherein, wherein respective portions of the infrastructure are managed oroperated by the MSO and one or more MNOs.

FIGS. 4-14 © Copyright 2020 Charter Communications Operating, LLC. Allrights reserved. Other Figures© Copyright of their respective copyrightholders.

DETAILED DESCRIPTION

Reference is now made to the drawings wherein like numerals refer tolike parts throughout.

As used herein, the term “access node” refers generally and withoutlimitation to a network node which enables communication between a useror client device and another entity within a network, such as forexample a 3GPP eNB or gNB, femtocell, small-cell, or CBRS CBSD.

As used herein, the term “application” (or “app”) refers generally andwithout limitation to a unit of executable software that implements acertain functionality or theme. The themes of applications vary broadlyacross any number of disciplines and functions (such as on-demandcontent management, e-commerce transactions, brokerage transactions,home entertainment, calculator etc.), and one application may have morethan one theme. The unit of executable software generally runs in apredetermined environment; for example, the unit could include adownloadable Java Xlet™ that runs within the JavaTV™ environment.

As used herein, the term “CBRS” refers without limitation to the CBRSarchitecture and protocols described in Signaling Protocols andProcedures for Citizens Broadband Radio Service (CBRS): Spectrum AccessSystem (SAS)—Citizens Broadband Radio Service Device (CBSD) InterfaceTechnical Specification—Document WINNF-TS-0016, Version V1.2.1. 3,January 2018, incorporated herein by reference in its entirety, and anyrelated documents or subsequent versions thereof.

As used herein, the terms “client device” or “user device” or “UE”include, but are not limited to, set-top boxes (e.g., DSTBs), gateways,modems, personal computers (PCs), and minicomputers, whether desktop,laptop, or otherwise, and mobile devices such as handheld computers,PDAs, personal media devices (PMDs), tablets, “phablets”, smartphones,wireless nodes such as FWA devices or femtocells/small-cells, andvehicle infotainment systems or portions thereof.

As used herein, the term “computer program” or “software” is meant toinclude any sequence or human or machine cognizable steps which performa function. Such program may be rendered in virtually any programminglanguage or environment including, for example, C/C++, Fortran, COBOL,PASCAL, assembly language, markup languages (e.g., HTML, SGML, XML,VoXML), and the like, as well as object-oriented environments such asthe Common Object Request Broker Architecture (CORBA), Java™ (includingJ2ME, Java Beans, etc.) and the like.

As used herein, the term “DOCSIS” refers to any of the existing orplanned variants of the Data Over Cable Services InterfaceSpecification, including for example DOCSIS versions 1.0, 1.1, 2.0, 3.0and 3.1.

As used herein, the term “headend” or “backend” refers generally to anetworked system controlled by an operator (e.g., an MSO) thatdistributes programming to MSO clientele using client devices, orprovides other services such as high-speed data delivery and backhaul.

As used herein, the terms “Internet” and “internet” are usedinterchangeably to refer to inter-networks including, withoutlimitation, the Internet. Other common examples include but are notlimited to: a network of external servers, “cloud” entities (such asmemory or storage not local to a device, storage generally accessible atany time via a network connection, and the like), service nodes, accesspoints, controller devices, client devices, etc.

As used herein, the term “LTE” refers to, without limitation and asapplicable, any of the variants or Releases of the Long-Term Evolutionwireless communication standard, including LTE-U (Long Term Evolution inunlicensed spectrum), LTE-LAA (Long Term Evolution, Licensed AssistedAccess), LTE-A (LTE Advanced), 4G LTE, WiMAX, VoLTE (Voice over LTE),and other wireless data standards.

As used herein, the term “memory” includes any type of integratedcircuit or other storage device adapted for storing digital dataincluding, without limitation, ROM, PROM, EEPROM, DRAM, SDRAM, DDR/2SDRAM, EDO/FPMS, RLDRAM, SRAM, “flash” memory (e.g., NAND/NOR), 3Dmemory, and PSRAM.

As used herein, the terms “microprocessor” and “processor” or “digitalprocessor” are meant generally to include all types of digitalprocessing devices including, without limitation, digital signalprocessors (DSPs), reduced instruction set computers (RISC),general-purpose (CISC) processors, microprocessors, gate arrays (e.g.,FPGAs), PLDs, reconfigurable computer fabrics (RCFs), array processors,secure microprocessors, and application-specific integrated circuits(ASICs). Such digital processors may be contained on a single unitary ICdie, or distributed across multiple components.

As used herein, the terms “MSO” or “multiple systems operator” refer toa cable, satellite, or terrestrial network provider havinginfrastructure required to deliver services including programming anddata over those mediums.

As used herein, the terms “MNO” or “mobile network operator” refer to acellular, satellite phone, WMAN (e.g., mmWave or 802.16), or othernetwork service provider having infrastructure required to deliverservices including without limitation voice and data over those mediums.The term “MNO” as used herein is further intended to include MVNOs,MNVAs, and MVNEs.

As used herein, the terms “network” and “bearer network” refer generallyto any type of telecommunications or data network including, withoutlimitation, hybrid fiber coax (HFC) networks, satellite networks, telconetworks, and data networks (including MANs, WANs, LANs, WLANs,internets, and intranets). Such networks or portions thereof may utilizeany one or more different topologies (e.g., ring, bus, star, loop,etc.), transmission media (e.g., wired/RF cable, RF wireless, millimeterwave, optical, etc.) and/or communications technologies or networkingprotocols (e.g., SONET, DOCSIS, IEEE Std. 802.3, ATM, X.25, Frame Relay,3GPP, 3GPP2, LTE/LTE-A/LTE-U/LTE-LAA, 5GNR, WAP, SIP, UDP, FTP,RTP/RTCP, H.323, etc.).

As used herein the terms “5G” and “New Radio (NR)” refer withoutlimitation to apparatus, methods or systems compliant with 3GPP Release15, and any modifications, subsequent Releases, or amendments orsupplements thereto which are directed to New Radio technology, whetherlicensed or unlicensed.

As used herein, the term “server” refers to any computerized component,system or entity regardless of form which is adapted to provide data,files, applications, content, or other services to one or more otherdevices or entities on a computer network.

As used herein, the term “storage” refers to without limitation computerhard drives, DVR device, memory, RAID devices or arrays, optical media(e.g., CD-ROMs, Laserdiscs, Blu-Ray, etc.), or any other devices ormedia capable of storing content or other information.

As used herein, the term “xNB” refers to any 3GPP-compliant nodeincluding without limitation eNBs (eUTRAN) and gNBs (5G NR).

Overview

In one exemplary aspect, the present disclosure provides improvedmethods and apparatus for enhanced wireless services which, inter alia,enable a client device (e.g., a 3GPP-compliant UE or mobile device) tomanage or prioritize its connection across two or more mobile networks(e.g., PLMNs), including those of respective different operators and/orthose of different types, such as for managing paging notifications.

In one embodiment, the existing 3GPP-based network paging model isextended so that the client device is aware of, and can process, pagingnotifications from the different networks and applications. Rather thanusing ToS as in the prior art, this embodiment uses enhanced URSP (UERoute Selection Policy) rules which enable paging causes send to theenhanced client device (UEe) to be correlated to Data Network Name (DNN)values specified by the user of the UEe.

In one implementation of the enhanced paging model above, the multi-USIMUE advantageously leverages the paging cause, which is based on DataNetwork Name (DNN) mapping performed by the network, such that thepaging notifications are prioritized according to the importance oftheir associated applications, while a separate IP address is maintainedfor each application.

For instance, in one implementation, the operator network includes aportal (e.g., “Application Function”) to allow the multi-USIM UEe userto group their important applications in a prioritized fashion such as:(i) “urgent,” wherein a multi-USIM UE will receive notifications in anyoperational condition, (ii) “default,” wherein the multi-USIM UE willreceive notifications when it is not otherwise busy, or (iii) “ignore,”wherein the multi-USIM UE does not receive notifications unless certaincriteria are met (e.g., during certain time-period/day).

The enhanced Multi-USIM UEe as described herein can accordinglydifferentiate between the urgent and non-urgent paging notifications, ineffect determining if a current session needs to be interrupted or notfor replying to paging requests from another network.

Moreover, with such enhancements, a multi-USIM UEe can also operate ineither PLMN (e.g., a “visited” or secondary PLMN, and a Home PLMN) so asto preserve services that require urgent response (such as importantpacket data functions which would otherwise be interrupted or ignored).

Advantageously, only comparatively minor modifications to extant 5Ginfrastructure and protocols are required to support the foregoingfunctionality.

Detailed Description of Exemplary Embodiments

Exemplary embodiments of the apparatus and methods of the presentdisclosure are now described in detail. While these exemplaryembodiments are described in the context of the previously mentionedwireless access networks (e.g., 5G NR) associated with or supported atleast in part by a managed network of a service provider (e.g., MSOand/or MNO networks), other types of radio access technologies (“RATs”)and other types of networks and architectures that are configured todeliver digital data (e.g., text, images, games, software applications,video and/or audio) may be used consistent with the present disclosure.

It will also be appreciated that while described generally in thecontext of networks providing service to a customer or consumer or enduser or subscriber (i.e., within a prescribed service area, venue, orother type of premises), the present disclosure may be readily adaptedto various types of environments including, e.g., within an enterprisedomain (e.g., businesses), or even governmental uses. Yet otherapplications are possible.

Moreover, the various aspects of the disclosure may be utilizedconsistent with various types of radio frequency spectrum (as well asthe underlying RAT technologies), including licensed, unlicensed (e.g.,LTE-U or LTE-LAA, or NR-U), or “quasi-licensed” spectrum such as CBRSspectrum, or even mmWave (e.g., such as 52.6-71 GHz ostensibly specifiedby 3GPP Release-17). Such spectrum types may be mixed as well, such aswhere a small-cell based network operates with unlicensed orquasi-licensed spectrum, and the macrocell network utilizes licensedspectrum.

Also, while certain aspects are described primarily in the context ofthe well-known Internet Protocol (described in, inter alia, InternetProtocol DARPA Internet Program Protocol Specification, IETF RCF 791(September 1981) and Deering et al., Internet Protocol, Version 6 (IPv6)Specification, IETF RFC 2460 (December 1998), each of which isincorporated herein by reference in its entirety), it will beappreciated that the present disclosure may utilize other types ofprotocols (and in fact bearer networks to include other internets andintranets) to implement the described functionality.

Other features and advantages of the present disclosure will immediatelybe recognized by persons of ordinary skill in the art with reference tothe attached drawings and detailed description of exemplary embodimentsas given below.

Methodology

As a brief aside, it is illustrative to first understand the prior artapproach for paging notifications referenced previously (i.e., in the3GPP 5G NR context) in greater detail. Specifically, FIG. 3 illustratesthe prior art network-triggered service request operation proposed under3GPP TS 23.502 (see FIG. 4.2.3.3-1 thereof). As shown in FIG. 3 ,downlink data is sent to the UPF (Step 1), which notifies the SMF (Step2a). The SMF ACKs (Step 2b), and the data is downlinked to the SMF (Step2c) Specifically, the UPF forwards the downlink data packets towards theSMF if the SMF instructed the UPF to do so, and the SMF buffers thetransmitted data packets.

If the Paging Policy Differentiation feature is supported by the SMF andthe PDU Session type is “IP”, the SMF determines the Paging PolicyIndicator, and optionally a paging cause, based on the DSCP in the Typeof Service (ToS) (IPv4)/Traffic Class (TC) (IPv6) value from the IPheader of the received downlink data packet. The SMF also identifies thecorresponding QoS Flow from the QFI of the received DL data packet.

At Step 3a, Namf_Communication_N1N2MessageTransfer occurs, includingSUPI, PDU Session ID, N1 SM container (SM message), N2 SM information(QFI(s), QoS profile(s), CN N3 Tunnel Info, S-NSSAI, Area of validityfor N2 SM information, ARP, Paging Policy Indicator, paging cause, 5QI,N1N2TransferFailure Notification Target Address, Extended Bufferingsupport), or NF to AMF: Namf_Communication_N1N2MessageTransfer (SUPI, N1message).

When it supports Paging Policy Differentiation, the SMF determines thePaging Policy Indicator and may also determine a paging cause related tothe downlink data that has been received from the UPF or triggered theData Notification message, based on the DSCP. See TS 23.501 clause5.4.3. The SMF indicates the Paging Policy Indicator and the pagingcause in the Namf_Communication_N1N2MessageTransfer discussed above.

Per Step 4b, if the UE is in CM-IDLE state in 3GPP access, and the PDUSession ID received from the SMF in Step 3a has been associated with3GPP access and based on local policy the AMF decides to notify the UEthrough 3GPP access even when UE is in CM-CONNECTED state for non-3GPPaccess, the AMF may send a Paging message to NG-RAN node(s) via 3GPPaccess, including the paging cause.

Per Step 4c, if the UE is simultaneously registered over 3GPP andnon-3GPP accesses in the same PLMN, and the UE is in CM-CONNECTED statefor non-3GPP access and in CM-IDLE for 3GPP access, the AMF may decideto send the NAS Notification message containing the 3GPP Access Type tothe UE over non-3GPP access including the paging cause.

Per step 4d, if the UE is simultaneously registered over 3GPP andnon-3GPP accesses in the same PLMN, and the UE is in the CM-CONNECTEDstate for the non-3GPP access (and in CM-IDLE for the 3GPP access) andif the UE decides to not accept the incoming service the UE respondswith NAS Notification response message over the non-3GPP access toindicate the same to the network.

Per step 5, a Namf_Communication (transfer failure notification) is sentfrom the AMF to the SMF pursuant to the above response, and per Step 6,the UE may choose to respond to the paging or NAS notification messagebased on the paging cause value, by executing service request procedure.

Hence, in essence, under the prior art scheme of FIG. 3 , the DSCP valuefrom the incoming IP packet will be mapped to a paging cause over the Uu(radio) interface to the UE. However, under such prior art scheme, auser of the UE is not able to set the paging cause differently betweenIP packets from different applications or sources (e.g., Skype vs.WhatsApp, etc.). This disability underscores a salient feature of thepresent disclosure; i.e., the ability to selectively manage andprioritize IP packets from various sources, based on e.g., user-based(and/or network-based) rules. This management and control allows, amongother things, the user to structure situations if/when it receivespaging notifications from certain particular applications, includingwhen roaming or associating with a different PLMN.

Hence, referring now to FIGS. 4-6B, various embodiments of the methodsof paging prioritization from different wireless networks based on e.g.,application priority according to the present disclosure, are shown anddescribed in detail. It will be appreciated that while these methods aredescribed primarily in the context of a 3GPP-based (i.e., E-UTRAN and/or5G NR) architecture, the various methods are in no way so limited, andmay be readily adapted and applied to other types or configurations ofwireless systems. Such adaptation and application being within the skilllevel of the ordinary artisan given the present disclosure, includingother applications where a UE or mobile device includes two differentSIM or similar credentials and is capable of operation with twodifferent PLMNs.

FIG. 4 shows one embodiment of the generalized method for prioritizingpaging notifications by a multi-USIM UEe from different wireless networkaccording to the present disclosure. It will be recognized that whileFIG. 4 and various other methods and apparatus described subsequentlyherein are described in terms of application that are bound to aparticular network (e.g., the UE can be configured to associate WhatsAppwith PLMNa and Skype with PLMNb, or an IMS application associated withPLMNa while OTT video (e.g., Youtube) is associated with PLMNb), suchassociation or bonding is not a requirement of practicing the invention.

It will further be appreciated that certain embodiments of thedisclosure may be implemented such that a given application receivesheterogeneous treatment within the different PLMNs. For example, a Skypeapplication associated with a user device may be configured such thatnotification is implemented with a first priority/criteria set forPLMNa, but a different priority and/or criteria set (e.g., for relevanttime periods) for PLMNb. As such, the user can if desired, differentiatethe paging notification services provided by the network as describedherein “intra-app” based on network identity. This intra-appdifferentiation may also have other criteria associated therewith, suchas where the differentiated treatment on one PLMN versus another onlyapplies in certain time periods, user contexts such as e.g., userlocation (based on e.g., association with a given Cell ID, GPSreceiver-derived location), set of user apps then in use on the userdevice (e.g., when “App A” and “App B” are both active, then applydifferentiation; otherwise no differentiation), or even battery chargestate for the user (e.g., mobile) device.

As shown, the method 400 includes first managing (e.g., grouping orother designation) of user applications per step 401. As described ingreater detail below, such managing or grouping may include for instanceprioritization of applications, specification of certain behaviors orrules with respect to the application, or similar.

Per step 403, one or more rules are generated relating to theapplication(s). As discussed in greater detail below, these rules may begenerated by the user (e.g., via a portal or similar enhancedapplication function (AFe) configured to allow such rule generation andmanagement, by the network, by one or more third parties (e.g., thoseproviding the underlying service of an app), or combinations thereof.

Per step 405, the client device is configured for the generated rule(s).For instance, in one variant, the client includes logic to receive andprocess paging notifications from a given network according to therule(s), such that the paging requests are e.g., processed immediatelyunder any operational conditions, processed only when certainoperational or other conditions are met, ignored, etc.

Per step 407, the configured client subsequently receives the pagingnotifications, and processes them per step 409 according to the rule(s)which it is configured to implement.

Referring now to FIG. 4A, one implementation of the generalized methodof FIG. 4 is described in the context of an enhanced 3GPP MUSIM UE (UEe)with paging processing and discrimination capability as describedherein. As shown, the method 430 of FIG. 4A includes first prioritizingor grouping applications based on their level of importance per step431, and sending the prioritized or grouped applications list(s) to thenetwork. For instance, as described further herein, the network in oneembodiment includes a portal (e.g., AFe) that allows the multi-USIM UEeuser to logically or functionally group their applications, with a DataNetwork Name (DNN) being designated for each group.

Per step 433, the network generates enhanced UE Route Selection Policy(URSPe) rules. The URSPe rules are generated based on multi-USIM UEeinput from step 431. These rules allow the multi-USIM UEe to use adesignated DNN on a per-group basis. One example of URSPe rules is shownin FIG. 4B. As shown, a name format of “DNN x” (where x is an integer)is used in this embodiment, although other formats and conventions maybe used consistent with the disclosure.

As a brief aside, routing selection priorities for a 3GPP 5G NR UE asprovided from the network are specified as UE Route Selection Policy(URSP). The policy rules are maintained by the PCF and are initiallytransferred to the UE, such as during network registration or PacketData Unit (PDU) session establishment. The UE uses these policies tohelp determine which 3GPP or non-3GPP access to prioritize or preferwhen multiple options are available to it. Accordingly, the URSP canassist in mobile data offload to non-3GPP networks such as IEEE Std.802.11 (Wi-Fi). The URSP can further be used for selection of networkslices and PDU sessions for user plane traffic.

Returning to FIG. 4A, per step 435, the network forwards the enhanced(URSPe) rules to the multi-USIM UEe. Once the multi-USIM UEe receivesthe URSPe rules, it configures itself in one variant by assigning theapplications (as identified by their Application Identifier/TrafficDescriptor) to their respective DNN values (step 437). See e.g., 3GPP TS23.501 and 23.503, each incorporated by reference in its entiretyherein, regarding exemplary UE use of URSP data. For instance, in oneimplementation, the URSPe data can be used by the UEe of the presentdisclosure to setup PDU session establishment using a specific DNN valueper application. Per TS. 23.503 the UE Route Selection Policy (URSP) canbe used by the UE to (i) determine if a detected application can beassociated to an established PDU Session, (ii) can be offloaded (e.g.,to a non-3GPP access outside of a PDU Session), or (ii) can causeestablishment of a new PDU Session. In the exemplary implementation, theURSPe rule includes one Traffic descriptor that specifies the matchingcriteria, as set forth in TS 23.503, although it will be appreciatedthat other approaches may be used consistent with the disclosure.

Per step 439, the multi-USIM UEe determines if any pending notificationsexist (whether by a periodic polling mechanism, direct notificationmessage, or otherwise), and processes the first pending pagingnotification per step 441. The multi-USIM UEe determines applicationhandling according to the URSPe rules and lastly, per step 443,depending on the application handling/priority, the multi-USIM UEe mayrespond to the paging by establishing the user plan connection or ignorethe page notification by not establishing the user plan connection withthe paging network. The logic then returns to step 439, wherein anyremaining notifications are processed similarly to the first.

It will be appreciated that while the generalized embodiment of FIG. 4is cast in terms of client configuration and processing, the servingnetwork(s) themselves can in some embodiments also or alternatively beconfigured to implement the rule(s) on behalf of a given client. Forexample, see the methodology 450 of FIG. 4C, which is a logical flowdiagram illustrating another embodiment of a generalized method ofenhanced paging notification for a client device according to thepresent disclosure, wherein network-based processing is utilized.Specifically, in this embodiment, the method 450 includes first managing(e.g., grouping or other designation) of user applications as describedelsewhere herein, per step 451.

Per step 453, one or more rules are generated relating to theapplication(s). As discussed elsewhere herein, these rules may begenerated by the user (e.g., via a portal or similar enhancedapplication function (AFe) configured to allow such rule generation andmanagement, by the network, by one or more third parties (e.g., thoseproviding the underlying service of an app), or combinations thereof.

Per step 455, the network is configured for the generated rule(s). Forinstance, in one variant, the network includes logic to receive incomingdata from an application source (e.g., remote network server) such asvia a network UPF (discussed below in greater detail with respect toFIG. 7 ) and process the data according to a prescribed rule set (ormultiple rule sets) in order to determine (i) whether pagingnotifications need be issued to the particular UEe, (ii) paging causemapping required, if any, and (iii) conduct of the paging according tothe rule(s), such that the paging requests are e.g., processedimmediately under any operational conditions, processed only whencertain operational or other conditions are met, ignored, etc. In thisregard, in contrast to the client-driven processing of the receivedpaging data discussed with respect to FIG. 4 , the embodiment of FIG. 4Callows the client device (UE) to be less capable (or even unenhanced;i.e., an off-the-shelf UE), since it can merely be configured to processall notifications it receives when they are received, with the upstreamnetwork processes determining how and when such notifications are to beissued to that UE per its particular rule set(s).

Per step 457, the client subsequently receives the paging notifications,and processes them per step 459 as it would any other pagingnotification.

Referring now to FIG. 5 , one embodiment of a method for processingapplications based on their level of importance is shown and described.This methodology is described in the context of the 3GPP-based URSPrule(s) shown in FIG. 4B, although it will be appreciated that it may beadapted to other rules and applications (including 3GPP and non-3GPPuses) by those of ordinary skill given the present disclosure.

Per step 501 of the method 500, while the multi-USIM UEe is connected toits current data network (e.g., PLMNa), an application routed throughanother data network (e.g., PLMNb) sends the multi-USIM UEe a pagingnotification.

Per step 503, the multi-USIM UEe determines whether the notification isassociated with an application which needs “urgent” response. In thisembodiment, the “urgent” applications are placed in Group1 as shown inFIG. 4B. The multi-USIM UEe receives notifications from these Group 1applications even when the multi-USIM UEe is engaging in a communicationsession (in RRC Connected state) with its current data network (e.g.,PLMNa). If the application is an urgent application, the method proceedsto step 515, otherwise it proceeds to step 505.

Per step 505, the multi-USIM UEe next determines whether the applicationis a “default” application (Group 2); the multi-USIM UEe receivesnotifications from these applications only when it is not engaged in acommunication session with its current data network (e.g., PLMNa) perstep 517. If the application is a default Group application, the methodproceeds to step 517, otherwise it proceeds to step 507.

Per step 507, the multi-USIM UEe determines whether the application isan “ignore for now” application; the “ignore for now” applications areplaced in Group 3, and the multi-USIM UEe does not receive pagingnotifications from these applications unless certain criteria are met;e.g., it is within certain time-period/date (e.g., the UEe receivesnotifications from these applications after midnight but before 4 AM, oronly during a weekend).

If Group 3, then per step 509, the multi-USIM UEe determines whether theapplication is within the prescribed time-period, during which suchpaging notifications are allowed to be processed (e.g., establish userplane connection). If the paging notification is within certaintime-period, the method 500 proceeds to step 515; otherwise it proceedsto step 511, wherein the UEe does not process the notification (e.g.,does not establish user plane connection).

Referring now to FIG. 6 , one embodiment of a method 600 for processingpaging notifications for a multi-USIM UEe within a mobile network isdescribed.

Per step 601 of the method 600, the network receives the multi-USIM UEeinput regarding the prioritization applications, such as directly fromthe UEe or via an AFe as described elsewhere herein. For instance, inone embodiment, the multi-USIM UEe designates applications which arecorrelated to DNNs, with each DNN corresponding to a unique IP addressto be assigned to UE as source IP address. As an example, theapplications belonging to Group 1 are assigned to DNN 1, whichcorresponds to IP address WWW.XXX.YYY.ZZZ. Likewise, the applicationsthat belong to Group 2 are assigned to DNN 2, which corresponds to IPaddress AAA.BBB.CCC.DDD, and so forth.

Per step 602, the network generates one or more URSPe rule sets (e.g.,FIG. 4B) according to the reported input from the multi-USIM UEe at step501. As previously noted, these URSPe rules define the applicationprecedence, and associate the applications traffic to different DNNs.

Per step 611, the network (UPF) receives the IP packets from the sourcesassociated with the application(s)—such as a remote or networked packetserver—and evaluates the destination IP address field used in their IPpacket. In this embodiment, the designated IP addresses of the packetsare used to determine the paging notification type such as e.g.,“urgent,” “normal” or “ignore for now” and are specific to particularUEe.

Per step 613, if the IP address is equivalent to a prescribed value(e.g., IP1), the method proceeds to step 615, where the SessionManagement Function (SMFe; see discussion of FIG. 7 below) in thenetwork maps the paging cause value to “urgent.” In this case, if themulti-USIM UEe is actively communicating with its current networks(e.g., PLMNa), it will disconnect from its current network, and connectto the other network (e.g., PLMNb) as required.

Per step 617, if the IP address is equivalent to another prescribedvalue such as IP2, the method proceeds to step 625, where the SMFe inthe network maps the paging cause to “normal.” Since this is a defaultbehavior, the network may or may not map this to paging cause dependingon its current connectivity. For example, if the multi-USIM UEe isactively communicating with its current network (e.g., PLMNa), it doesnot answer to the paging request. On the other hand, if the multi-USIMUEe is not actively communicating to its current network (e.g., PLMNa),then it will answer the paging request.

Per step 619, if the IP address is equivalent to e.g., IP3, the methodproceeds to step 621, and if the paging has been requested within acertain time period/day (e.g., after midnight, weekend), it proceeds tostep 627. Otherwise, the method proceeds to step 623, and the SMFeinstructs the UPF to discard these packets.

Per step 627, since the paging has occurred within the certain timeperiod/day, the SMFe maps the paging cause to “allow,” and themulti-USIM UEe answers the paging request.

Referring to FIG. 6A, one specific implementation of step 609 of method600 is shown and described.

Per step 633, the enhanced Policy Control Function (PCFe) in the networkreceives the URSPe rules from the Application Function (AFe). The USRPerules are stored in Unified Data Repository (UDR) or associated storage(see discussion of FIG. 7 below).

Per step 635, the PCFe sends the URSPe rules to the ApplicationManagement Function (AMF).

Lastly, per step 637, the receiving AMF sends the URSPe rules to themulti-USIM UEe via the NG-RAN and Uu air interface.

As a brief aside, when a UEe attaches to the network, the PCFe receivesthe URSPe rules for this particular UEe from the UDR. If the URSPe rulesare modified, the PCFe receives a new URSPe rules from the UDR, andforwards the new rules to the multi-USIM UEe. As such, the UEe isconstantly kept informed of the latest iteration of the USRPe rules.

Referring now to FIG. 6B, one specific implementation of step 611 ofmethod 600 is shown and described.

Per step 653, the User Plane Function (UPF) of the networkscreens/processes the incoming IP packets received at the network, suchas from a remote IP packet source or application server.

Per step 655, if the N3 interface is connected (a GTP tunnel exists forthis multi-USIM UEe), and the UPF maps the resulting paging cause basedon the IP address of the incoming packet (i.e., the destination UEe) atstep 657. Furthermore, on the N4 interface, information is added toindicate paging cause mapping rules for one or more DNN values. Forinstance, IP traffic from DNN 1 will map to paging cause 2, IP trafficfrom DNN 2 will map to paging cause 4, and so forth. If the N3 interfaceis not connected (e.g., the multi-USIM UEe is in idle state), the methodproceeds to step 665, and uses the N4 interface to forward the IP packetheader to the SMFe.

Per step 666, the SMFe maps the paging cause based on the UE's IPaddress received from packet header.

Per step 667, the SMFe incudes the paging cause in aNamf_Communication_N1N2MessageTransfer message; then the AM sends thepaging cause to the NG-RAN.

Per steps 661 and 663, the NG-RAN receives the transmitted paging causeand sends it to the multi-USIM UE via the Uu interface. When themulti-USIM UEe receives the paging cause, the multi-USIM UEe can usethis paging cause to determine the response to the network (e.g., alertthe user, reject the paging, ignore the paging, receive the paging anddata while keeping the phone in the silent node, etc.).

Network Architecture for Paging Prioritization—

Referring now to FIG. 7 , one exemplary embodiment of a 5G networkconfiguration for implementing managed or prioritized paging proceduresaccording to the present disclosure is shown and described.Specifically, as shown in FIG. 7 , the architecture 700 includes one ormore enhanced UE (UEe) 715 having multiple USIMs and DSDS capability,one 5G NG-RAN 709, an enhanced AF (AFe) 713, an enhanced PCF (PCFe) 717,an enhanced SMF (SMFe) 705, a UPF 707, as well as a UDR 701 andassociated storage 703 for storing URSP/USPRe rules and policies. Itwill be appreciated that both traditional or extant USRP policies andrules (“USRP rules”) as well as enhanced policies and rules whichinclude application and notification differentiation as described herein(“USRPe rules”) may each be managed and stored by the network.

Although one NG-RAN 709 is shown in FIG. 7 , it will be appreciated thatconfigurations with different numbers of and/or other type of RANs maybe utilized consistent with the present disclosure in addition to thosedescribed subsequently herein.

In the exemplary embodiment, the UEe 715 groups the applications basedon their priority, and sends the list of applications in each group tothe AFe 713 (such as via the OTT process shown). Furthermore, in theexemplary embodiment, the user subscription records as well asUSRP/URSPe rules for the UEe 715 are stored in the UDR policy storagedatabase 703, via use of a Q&M interface 717 from the AFe 713.

As noted previously, various policies or rules can be specified in orderto provide “differentiated” paging and packet delivery functions withinthe architecture 700. As further examples certain applicationsassociated with the UEe (e.g., App. 1, App. 2) may be grouped to use aparticular DNN value (e.g., DNN 1), as previously described. IP trafficassociated with DNN1 can be pages with a first paging cause value (e.g.,X1). In one variant, the paging cause is encoded as a numeric value from0 to 7 (e.g., 000 to 111 when encoded using three bits). The value “X1”can be mapped to e.g., the integer value “4” in that range. Similarly, avalue of “0” can be reserved for highest (e.g., emergency) prioritypaging causes. Other values may be reserved by the operator such as for3GPP IP Multimedia System (IMS) services.

As shown, when the UEe 715 attaches the network 700, the PCFe 710receives the URSP/USRPe rules from the UDR 701 via the interface N36,forwards these rules to the AMF 711 via the interface N15, and then theAMF 711 forwards the URSP/USRPe rules to the UEe 715 via interface N1.Notably, the IP traffic received at the UPF (e.g., from a networkedapplication server or other source) is sent from NG-RAN 709 to the UEe715 via the Uu interface 727.

If the USRPe rules are modified, for instance when the priority ofapplications changes based on user input, the PCFe 710 receives newURSPe rules data from the UDR 701, and then forward these new rules tothe UEe 715 via interfaces N15 and N1 through the AMF 711.

The UPF 707 processed the incoming IP traffic (which in this case is“differentiated” based on certain traffic being associated withdifferent IP addresses which are each associated with the UEe 715) viathe N6 interface 719, and forwards the traffic to the appropriate UEe.As described herein previously, if the UEe is in RRC CONNECTED or RRCINACTIVE state, the UPF 707 utilizes the N3 interface 721 to forward theIP traffic to the UEe 715. Otherwise, when the UEe is in RRC IDLE state,the UPF utilizes the N4 interface 723 to forward the IP traffic to theUEe 715.

Also, present in the architecture of FIG. 7 , is a modified N4 interface723. In the present embodiment, a new information capability is added tothe N4 interface which may be used to indicate the paging cause mappingrule for DNNx values. For instance, IP traffic from DNN 1 will map topaging cause 2; IP traffic from DNN 2 will map to paging cause 4, and soforth. The paging cause is in one embodiment placed in the GTP header,and is sent to NG-RAN via the N3 interface 721 (or via the N11/N2interfaces and the AMF 711).

Furthermore, in the present architecture, the PCFe 710 installs a PolicyControl and Charging (PCC) rule on the SMFe 705 via the interface N7,which adds new information to the paging cause mapping rule in order tomap the IP traffic to the appropriate paging cause values. For instance,IP traffic from DNN 1 will map to paging cause 2, and IP traffic fromDNN 2 will map to paging cause 4 in the above example.

FIG. 7A is a ladder diagram illustrating an exemplary communication flowbetween the UEe 715, data store 703, AFe 713, PCFe 710, SMFe 705, UDR701, UPF 707, and AMF 711 referred in FIG. 7 .

Referring now to FIG. 8 , an exemplary embodiment of networkconfiguration for implementing the managed/prioritized paging procedurein roaming scenarios according to the present disclosure is shown anddescribed.

Specifically, as shown in FIG. 8 , the architecture 800 includes one ormore enhanced UE (UEe) 715 having multiple USIMs, as well as Home PLMN(HPLMN) 825 and Visited PLMN (VPLMN) 823, although it will beappreciated that configurations with different numbers of and/or othertypes of PLMNs and/or RANs may be utilized consistent with the presentdisclosure in addition to those described subsequently herein. HPLMN andVPLMN may belong to the same or different network operators or types ofoperators (e.g., MNOs and/or MSOs, or other types of entities). In thisexemplary embodiment, the UEe 715 subscriber profile is configured inthe HPLMN 805 (the home network of the subscriber, such as one managedby the MSO). VPLMN 823 shares its coverage with HPLMN 825 when the UEeleaves the HPLMN 825. As a brief aside, the N9 interface provides (H)UPFto (V)UPF communication, the N16 interface provides (H)SMFe to (V)SMF(or (V)SMFe) communication, and the N24 interface provides (H)PCF to(V)PCF(e) interface.

In the illustrated configuration 800, the user subscription record aswell as URSP/USPRe rules for the UEe 715 are stored in the UDR database701 in the HPLMN 805. As shown, when the UEe 715 attaches to the visitednetwork 823, the VPCF 810 receives the URSP/USRPe rules from the UDR 701via the HPCFe 710. The AMF 811 receives the URSP/USRPe rules from theVPCH 810 via the interface N15, and forwards to the UEe via the N1interface.

Also, in the present architecture, the HPCFe 710 installs a PolicyControl and Charging (PCC) rule on the HSMFe 705 via the interface N7,which adds new information to the paging cause mapping rule in order tomap the IP traffic to the appropriate paging causes. The VSMF 805receives the mapping rule and paging cause from the HSMFe 705 via theN16 interface, which is forwarded to the UEe 715 via AMF 811 and theinterface N11 and N2 to the NG-RAN.

The (H)UPF 707 screens the incoming IP traffic received via the N6interface 719, and forwards the traffic to the appropriate UEeapplication/process based on IP address. As described herein previously,if the UEe is in RRC CONNECTED state, the HUPF 707 sends the incoming IPpackets to the VUPF 807 via the N9 interface 828, and then the VUPF 807utilizes the N3 interface 721 to forward the IP traffic to the UEe 715.Otherwise, when the UEe is in RRC IDLE state, the HUPF 707 utilizes theN4 interface 723 to forward the IP traffic to the HSMF 705, and then theHSMF 705 forwards the VSMF 805 via the interface 826. The VSMF 805receives the IP traffic, and forwards it to the UEe 715, via AMF and theN15 interface 725.

It will also be recognized that mechanisms for maintaining IP addresscontinuity across various different networks such as two PLMNs (e.g., aVPLMN and HPLMN, such as where one is an enterprise network havingoverlapping coverage with a larger cellular or MNO PLMN) may also beutilized consistent with the architecture 800 of FIG. 8 . For example,the methods and apparatus described in co-owned and co-pending U.S.patent application Ser. No. 16/842,352 filed Apr. 7, 2020 entitled“APPARATUS AND METHODS FOR INTERWORKING IN WIRELESS NETWORKS,” andissued as U.S. Pat. No. 11,564,155 on Jan. 24, 2023, incorporated hereinby reference in its entirety, may be used for such purposes.

PCFe Apparatus—

FIG. 9 illustrates an exemplary embodiment of an enhanced 5G PCF (PCFe)apparatus 710, useful for operation in accordance with the presentdisclosure.

In one exemplary embodiment as shown, the PCFe 710 includes, inter alia,a processor apparatus or subsystem 903, a program memory module 911,mass storage device 909, and network interfaces 907 for communicationswith the relevant 5G-RAN or other entities such as SMF/SMFe 705previously described herein, the NG-RAN 709, and the UDR 710.

In the exemplary embodiment, the processor 903 may include one or moreof a digital signal processor, microprocessor, field-programmable gatearray, or plurality of processing components mounted on one or moresubstrates. The processor 903 may also comprise an internal cachememory, and is in communication with a memory subsystem 911, which cancomprise, e.g., SRAM, flash and/or SDRAM components. The memorysubsystem may implement one or more of DMA type hardware, so as tofacilitate data accesses as is well known in the art. The memorysubsystem of the exemplary embodiment contains computer-executableinstructions which are executable by the processor 903. In addition, thePCFe 710 may include URSP logic 913 in the program memory which is incommunication with the processing subsystem to support prioritizedapplication processing as dictated by the UEe 715 (as well as 5G stack915 to implement other 5G NR related functions of the PCFe). In oneexample, the URSPe and 5G stack logic maybe implemented on a storagedevice and executed on the processor 911.

The processing apparatus 903 is configured to execute at least onecomputer program stored in memory 911 (e.g., the logic of the URSPerules according to the methods of FIGS. 4-6B, herein, in the form ofsoftware or firmware that implements the various functions). Otherembodiments may implement such functionality within dedicated hardware,logic, and/or specialized co-processors Snot shown).

In some embodiments, the logic 913 and 915 also utilize memory 911 orother storage 909 configured to temporarily hold a number of datarelating to the various rules, policies, applications or other datautilized by the UEe 715 (whether alone or in conjunction with the massstorage device 909) which it services under the 5G NR standard(s). Inother embodiments, application program interfaces (APIs) such as thoseincluded in an MSO-provided application or those natively available onthe PCFe may also reside in the internal cache or other memory 911. SuchAPIs may include common network protocols or programming languagesconfigured to enable communication with the PCFe 710 and other networkentities (e.g., via API “calls” to the PCFe by MSO network processestasked with gathering load, configuration, subscriber, or other data).

SMFe Apparatus—

FIG. 10 illustrates an exemplary embodiment of a 5G enabled SMF (SMFe)apparatus 705, useful for operation in accordance with the presentdisclosure.

In one exemplary embodiment as shown, the SMFe 705 includes, inter alia,a processor apparatus or subsystem 1003, a program memory module 1011,mass storage device 1009, and network interfaces 1007 for communicationswith the relevant 5G-RAN or other entities such as the PCF/PCFe 710previously described herein, the NG-RAN 709, and the UDR 710.

In the exemplary embodiment, the processor 1003 may include one or moreof a digital signal processor, microprocessor, field-programmable gatearray, or plurality of processing components mounted on one or moresubstrates. The processor 1003 may also comprise an internal cachememory, and is in communication with a memory subsystem 1011, which cancomprise, e.g., SRAM, flash and/or SDRAM components. The memorysubsystem may implement one or more of DMA type hardware, so as tofacilitate data accesses as is well known in the art. The memorysubsystem of the exemplary embodiment contains computer-executableinstructions which are executable by the processor 1003. In addition,the SMFe 705 may include URSPe logic 1013 in the program memory which isin communication with the processing subsystem to support managed orprioritized application processing instructed by the UEe 715 via itsUSRP rules generated from the AFe 713 (as well as 5G stack 1015 toimplement other 5G NR related function of SMFe). For instance, the SMFeUSPRe logic 1013 may map user rules regarding individual applicationsand DNN values to particular paging causes as described elsewhereherein.

The processing apparatus 1003 is configured to execute at least onecomputer program stored in memory 1011 (e.g., the logic of the URSPerules according to the methods of FIGS. 4-6B, herein, in the form ofsoftware or firmware that implements the various functions). Otherembodiments may implement such functionality within dedicated hardware,logic, and/or specialized co-processors not shown).

In some embodiments, the logic 1013 and 1015 also utilizes memory 1011or other storage 1009 configured to temporarily hold a number of datarelating to the various USPRe rules, policies, applications, IPaddresses, DNN values, or other data utilized for a given UEe 715 whichit services under the 5G NR standard(s). In other embodiments,application program interfaces (APIs) such as those natively availableon the SMFe may also reside in the internal cache or other memory 911.Such APIs may include common network protocols or programming languagesconfigured to enable communication with the PCF_(e) 710, UPF 709 andother network entities (e.g., via API “calls” to the SMFe by MSO networkprocesses tasked with gathering load, configuration, subscriber, DNN, IPaddress, or other data, or vice versa).

AFe Apparatus—

FIG. 11 illustrates an exemplary embodiment of a 5G enhanced AF (AFe)apparatus 713, useful for operation in accordance with the presentdisclosure.

In one exemplary embodiment as shown, the AFe 705 includes, inter alia,a processor apparatus or subsystem 1103, a program memory module 1111,mass storage device 1109, and network interfaces 1107 for communicationswith the relevant 5G-RAN or other entities such as PCF/PCFe 710previously described herein, the NG-RAN 709, and the UDR 710, as well asan MSO or MNO data backbone, such as to enable access to the AFe 713 bya user via the Internet (e.g., a web portal or similar function). Itwill be appreciated that in various embodiments of the disclosure, theUEe/user may access the AFe to provide input or feedback on its desiredmanagement/prioritization functionality (e.g., application assignment toDNN groups) via (i) an app executing on the UEe and configured tocontact the AFe via the NG-RAN 709 and interposed components, (ii) via auser's access of an MSO or MNO website (whether by the UEe or anotheruser device such as a PC), or (iii) yet other approaches, such as via athird-party network-based proxy process such as e.g., an Amazon Alexacloud-based skills platform (e.g., “Alexa . . . change my SkypeApplication Notification Profile to “Travel Profile” . . . ”), which iscommunicative with the AFe 713 and which utilizes APIs to e.g., obtaindata on desired user-specific profiles.

In the exemplary embodiment, the AFe processor 1103 may include one ormore of a digital signal processor, microprocessor, field-programmablegate array, or plurality of processing components mounted on one or moresubstrates. The processor 1103 may also comprise an internal cachememory, and is in communication with a memory subsystem 1111, which cancomprise, e.g., SRAM, flash and/or SDRAM components. The memorysubsystem may implement one or more of DMA type hardware, so as tofacilitate data accesses as is well known in the art. The memorysubsystem of the exemplary embodiment contains computer-executableinstructions which are executable by the processor 1103. In addition,the AFe 713 may include URSPe logic 1113 in the program memory which isin communication with the processing subsystem to support prioritizedapplication processing rules as instructed by the UEe 715, as well as a5G stack 1115 to implement other 5G NR related functions of the AFeincluding communication protocols with other 5G entities.

The processing apparatus 1103 is configured to execute at least onecomputer program stored in memory 1111 (e.g., the logic of the URSPerules according to the methods of FIGS. 4-6 , herein, in the form ofsoftware or firmware that implements the various functions). Otherembodiments may implement such functionality within dedicated hardware,logic, and/or specialized co-processors not shown.

UEe Apparatus—

FIG. 12 illustrates a block diagram of an exemplary embodiment of a UEe715, useful for operation in accordance with the present disclosure.

In one exemplary embodiment as shown, the UEe 715 includes, inter alia,a processor apparatus or subsystem such as a CPU 1203, flash memory orother mass storage 1229, a program memory module 1211, 4G basebandprocessor module 1209 b with 4G/4.5G stack 1224, 5G baseband processormodule 1209 a with 5G NR stack 1222, and 5G wireless radio interface1210 and 4G/4.5G radio interface 1212 for communications with therelevant RANs (e.g., 5G-NR RAN and 4G/4.5G RAN) respectively, andultimately components of the EPC or NG Core 1235 or the AFe 713 asapplicable. The RF interfaces 1210, 1212 are configured to comply withthe relevant PHY standards which each supports, and include an RF frontend 1210, 1216 and antenna(s) elements 1248, 1249 tuned to the desiredfrequencies of operation (e.g., 5 GHz or 52.6-71 GHz for the 5G array,and e.g., 5 GHz for the LTE/LTE-A bands). Each of the UEe radios includemultiple spatially diverse individual elements in e.g., a MIMO- orMISO-type configuration, such that spatial diversity of the receivedsignals can be utilized. For example, an exemplary Qualcomm QTM052mmWave antenna module may be used within the UEe device for mmWavereception and transmission. Beamforming and “massive MIMO” may also beutilized within the logic of the UE device.

In one embodiment, the various processor apparatus 1203, 1209 a, 1209 bmay include one or more of a digital signal processor, microprocessor,field-programmable gate array, GPU, or plurality of processingcomponents mounted on one or more substrates. For instance, an exemplaryQualcomm Snapdragon x50 5G modem may be used consistent with thedisclosure as the basis for the 5G BB processor 1209 a.

The various BB processor apparatus 1209 a, 1209 b may also comprise aninternal cache memory, and a modem.

The program memory module 1211 may implement one or more of directmemory access (DMA) type hardware, so as to facilitate data accesses asis well known in the art. The memory module of the exemplary embodimentcontains one or more computer-executable instructions that areexecutable by the CPU processor apparatus 1203.

Other embodiments may implement the application management andnotification processing module/logic 1206 functionality within dedicatedhardware, logic, and/or specialized co-processors (not shown). Inanother embodiment, the module logic 1206 is integrated with the CPUprocessor 1203 (e.g., via on-device local memory, or via execution onthe processor of externally stored code or firmware).

In some embodiments, the UEe 715 also utilizes memory 1211 or otherstorage configured to temporarily hold a number of data relating toe.g., the various application configurations for various modes. Forinstance, when presented with a paging cause by the network, the UEe mayrecall data relating to particular processing rules associated with thatpaging cause (e.g., based on association with the paging cause to aparticular DNNx value). Rules for different networks, user contexts(e.g., “traveling,” “at home,” “at office,” “do not disturb” and thelike) may also be stored within the UEe.

Also included in the UEe 715 is a USIM apparatus 1227, which isconfigured to securely store (and provide ancillary processing relatedto), which enables the UEe to register within the two separate networks(e.g., the HPLMN and VPLMN, respectively in FIG. 8 ). In one embodiment,the 4G/5G GUTIs are received by the UEe pursuant to registration/attachprocedures, and stored within the USIM 1227 in respective storageelements thereof (e.g., SE's or cryptographically secure elements).

In some embodiments, the UEe logic also utilizes memory 1211 or otherstorage 1229 configured to temporarily hold a number of data relating tovarious PLMN associations for the various services/applications such asvoice, etc.) for the various functions described herein.

In other embodiments, application program interfaces (APIs) such asthose included in an MSO-provided application or those nativelyavailable on the UEe may also reside in the internal cache or othermemory 1211. Such APIs may include common network protocols orprogramming languages configured to enable communication with the UEeand other network entities (e.g., via API “calls” to the UEe by MSOnetwork processes tasked with gathering paging, application load,configuration, usage of PLMNs, or other data). As an aside, adownloadable application or “app” may be available to subscribers of anMSO or cable network (and/or the general public, including MSO “partner”MNO subscribers), where the app allows users to configure their UEe viathe UI 1232 to implement enhanced functionality, including interfacewith the AFe 713, data collection and reporting back to the AFe/MSO corenetwork, and other functions so as to enable, inter alia, service/RANavailability when roaming, congestion, or other attributes which may beuseful in implementing e.g., the methodologies of FIGS. 4-6B discussedabove. Application program interfaces (APIs) may be included inMSO-provided applications, installed with other proprietary softwarethat comes prepackaged with the UEe. Alternatively, the relevant MNO mayprovide its subscribers with the aforementioned functionality (e.g., asa pre-loaded app on the UEe at distribution, or later via download), oras a firmware update to the UEe stack conducted OTA.

Other applications making use of e.g., IP data sessions, such as instantmessaging or other social media (e.g., Skype, WhatsApp, etc.), VPN apps,VoIP apps, banking apps, and similar may also be installed and operativeon the UEe 715.

Service Provider Networks

FIG. 13 illustrates a typical service provider network configurationuseful with the features of the apparatus and methods described herein.It will be appreciated that while described with respect to such networkconfiguration, the methods and apparatus described herein may readily beused with other network types and topologies, whether wired (e.g.,copper or optical) or wireless, managed or unmanaged.

The exemplary service provider network 1300 is used in the embodiment ofFIG. 13 to provide backhaul and Internet access from the serviceprovider's wireless access nodes (e.g., eNB, gNB or Node B NR-U)devices, Wi-Fi APs, and FWA devices operated or maintained by the MSO),and one or more stand-alone or embedded DOCSIS cable modems (CMs) 1305in data communication therewith. It will be appreciated that the xNB andUEe devices described herein may operate on licensed, unlicensed, orquasi-licensed/shared access spectrum while utilizing the underlying3GPP 4G/5G NR/NR-U based protocols described herein.

The individual xNB's 1301 are backhauled by the CMs 1305 to the MSO corevia e.g., CMTS or CCAP MHAv2/RPD or other such architecture, and the MSOcore 1319 includes at least some of the EPC/5GC core functionspreviously described, as well as PCFe/SMFe/AFe network processes710,705,713 as shown. The enhanced network processes are in oneembodiment realized as one or more network-based servers whichcommunicates with the MSO infrastructure so as to effect variousfunctions, including those of FIGS. 4-6 as previously described.

Client devices 1311 such as tablets, smartphones, SmartTVs, etc. at eachpremises are served by respective WLAN routers 1307, IoT gateways 1317,and NR-U or CBRS capable CPEe/FWAe 1305, the latter which are backhauledto the MSO core or backbone via their respective xNB's, and whichthemselves may be enhanced with paging notification managementcapability to act in effect as fixed UEe. While such devices may not bemobile as in the exemplary UEe 715 previously described, they may residewithin the operational areas of two PLMNs (e.g., an MSO PLMN orsmall-cell PLMN served by e.g., CBRS or NR-U-enabled 3GPP CBSDs or gNBs,and an MNO macrocell network), and as such may selectively operatewithin both networks in the event that the fixed UEe includesDSDS/dual-USIM capability. As such, the present disclosure contemplatesservicing of any number of different configurations of UEe includingboth mobile and fixed devices, and a number of possible RAN and PLMNconfigurations (including femto-cell and small-cell “micro” PLMNsmaintained by multiple different subscribers or enterprises, includingthose operating within or adjacent to coverage areas of MSO or MNOmacrocells.

Notably, in the embodiment of FIG. 13 , all of the necessary componentsfor support of the wireless service provision and backhaul functionalityare owned, maintained and/or operated by the common entity (e.g., cableMSO). The approach of FIG. 13 has the advantage of, inter alia, givingthe MSO complete control over the entire service provider chain so as tooptimize service to its specific customers (versus the non-MSOcustomer-specific service provided by an MNO), and the ability toconstruct its architecture to optimize incipient 5G NR functions such asnetwork slicing, gNB DU/CU Option “splits” within the infrastructure,selection or configuration of subsets or groups of gNB (or theirindividual DU), etc. Also, the presence of the AFe 713 within the MSOdomain allows the MSO to control subscriber access and the interfaceexperience thereof; e.g., via an MSO-provided app for the UEe 715, awebsite or other portal functionality “branded” for the MSO andconfigured for its desired functions, and control over IP addressassignment for individual application/DNN values (e.g., the MSO maymaintain a semi-static or static pool of IP addresses for use byparticular UEe, classes of subscriber, etc.).

FIG. 14 illustrates another embodiment of the network architecture,highlighting one possible relationship between an MSO architecture andan MNO architecture. As shown, the MSO service domain extends only tothe CPEe/FWAe and served premises and the MSO core functions, whileother functions such as 3GPP EPC/E-UTRAN or 5GC and NG-RANfunctionality, as well as PCFe/SMFe/AFe functions, are provided by oneor more MNO networks 1423,1425 operated by MNOs (which may belong to thesame or different operators), including in some embodiments those withwhich the MSO has a service agreement. In this approach, at least someof the PCFe/SMFe/AFe are maintained and operated by the MNO, althoughthis is not a requirement, and the present disclosure contemplatesembodiments where portions of the paging cause mapping and notificationfunctionality is maintained by the MSO or even a third party. Theapproach of FIG. 14 (i.e., coordination of MSO and MNO networks) has theadvantage of, inter alia, avoiding more CAPEX by the MSO, includingduplication of infrastructure which may already service the area ofinterest, including reduced RF interference due to addition of extra(and ostensibly unnecessary) RAN components such as xNB's or othertransceivers.

Hence, depending on what data is useful to the MSO or its customers,various portions of the foregoing can be associated and stored toparticular xNB “clients” or their components being backhauled by the MSOnetwork, whether owned by the MSO, MNO, or another entity. These datacan also be utilized by e.g., a controller or another network process inIP data session and paging management processes for MUSIM UEe's withinthe infrastructure, such as based on operational loading of a given xNBor the network as a whole, UEe location relative to the xNB's,subscriber account or subscription level or privileges, presence ofother suitable backhauls for the UEe such as WLAN, 5G NR network slicingconsiderations, and/or yet other factors which will be recognized bythose of ordinary skill in the wireless infrastructure arts given thepresent disclosure. As such, operational load on the network may also bereduced via implementation of differentiated paging by the network,since unnecessary or undesired PDN sessions requested by the UEe 517 maybe reduced or obviated based on that UEe's particular USRP(e) rules anddesired paging behavior.

It will be recognized that while certain aspects of the disclosure aredescribed in terms of a specific sequence of steps of a method, thesedescriptions are only illustrative of the broader methods of thedisclosure, and may be modified as required by the particularapplication. Certain steps may be rendered unnecessary or optional undercertain circumstances. Additionally, certain steps or functionality maybe added to the disclosed embodiments, or the order of performance oftwo or more steps permuted. All such variations are considered to beencompassed within the disclosure disclosed and claimed herein.

While the above detailed description has shown, described, and pointedout novel features of the disclosure as applied to various embodiments,it will be understood that various omissions, substitutions, and changesin the form and details of the device or process illustrated may be madeby those skilled in the art without departing from the disclosure. Thisdescription is in no way meant to be limiting, but rather should betaken as illustrative of the general principles of the disclosure. Thescope of the disclosure should be determined with reference to theclaims.

It will be further appreciated that while certain steps and aspects ofthe various methods and apparatus described herein may be performed by ahuman being, the disclosed aspects and individual methods and apparatusare generally computerized/computer-implemented. Computerized apparatusand methods are necessary to fully implement these aspects for anynumber of reasons including, without limitation, commercial viability,practicality, and even feasibility (i.e., certain steps/processes simplycannot be performed by a human being in any viable fashion).

What is claimed is:
 1. A computerized method of managing pagingnotifications for a computerized client device, the computerized methodcomprising: generating data relating to one or more rules relating toone or more user applications, the one or more user applicationsassociated with the computerized client device; and causingconfiguration of the computerized client device according to thegenerated data relating to the one or more rules, the causing of theconfiguration comprising causing the computerized client device toexecute computerized logic to perform at least evaluation of a pluralityof paging notifications from one or more wireless networks according tothe one or more rules, each of the plurality of paging notificationsassociated with at least one of the one or more user applications. 2.The computerized method of claim 1, wherein the causing the computerizedclient device to execute the computerized logic to perform at least theevaluation of the plurality of the paging notifications from the one ormore wireless networks according to the one or more rules comprisescausing the computerized client device to selectively process or notprocess individual ones of the plurality of paging notifications basedon one or more criteria relating to the individual ones being met or notmet, respectively.
 3. The computerized method of claim 1, wherein thecausing the computerized client device to execute the computerized logicto perform at least the evaluation of the plurality of the pagingnotifications from the one or more wireless networks according to theone or more rules comprises causing the computerized client device toimplement a notification associated with the one or more userapplications with a first priority for a first PLMN (public land mobilenetwork), and a second priority that is different from the firstpriority for a second PLMN.
 4. The computerized method of claim 1,wherein the causing the computerized client device to execute thecomputerized logic to perform at least the evaluation of the pluralityof the paging notifications from the one or more wireless networksaccording to the one or more rules comprises causing the computerizedclient device to implement a first of the plurality of pagingnotifications that is associated with a first PLMN (public land mobilenetwork) with a higher priority than a second of the plurality of pagingnotifications that is associated with a second PLMN.
 5. The computerizedmethod of claim 1, wherein: the one or more user applications comprisesa plurality of user applications; the plurality of paging notificationsare each associated with different ones of the plurality of userapplications; and the causing the computerized client device to executethe computerized logic to perform at least the evaluation of theplurality of paging notifications from the one or more wireless networksaccording to the one or more rules comprises causing the computerizedclient device to at least evaluate a priority associated with each ofthe plurality of paging notifications.
 6. The computerized method ofclaim 5, wherein the at least evaluation of the priority associated witheach of the plurality of paging notifications comprises evaluation of atleast some of the priorities relative to others of the priorities inorder to prioritize the plurality of paging notifications relative toone another.
 7. The computerized method of claim 1, wherein thegenerating data relating to the one or more rules relating to the one ormore user applications, the one or more user applications associatedwith the computerized client device, comprises: receiving data generatedby a user of the computerized client device, the received data relatingto handling of notifications for at least some of the one or more userapplications; and generating the data relating to the one or more rulesbased at least on the received data.
 8. The computerized method of claim1, wherein: at least two of the plurality of paging notifications areassociated with a respective first PLMN (public land mobile network) andsecond PLMN; and the at least evaluation of the plurality of pagingnotifications from one or more wireless networks according to the one ormore rules, comprises: determining that a first of the at least two ofthe plurality of paging notifications is from one of the first PLMN orthe second PLMN with which the computerized client device is notcurrently maintaining an active session; determining that the first ofthe at least two of the plurality of paging notifications meets one ormore criteria for establishment of the active session with the one ofthe first PLMN or the second PLMN with which the computerized clientdevice is not currently maintaining the active session; and causing theestablishment of the active session with the one of the first PLMN orthe second PLMN with which the computerized client device is notcurrently maintaining the active session, so that the computerizedclient device can receive data associated with the first of the at leasttwo of the plurality of paging notifications.
 9. The computerized methodof claim 1, further comprising: determining a paging cause associatedwith one of the plurality of paging notifications; recalling rule datarelating at least to the determined paging cause; and performing furtherevaluation of the one of the plurality of paging notifications using atleast the recalled rule data.
 10. The computerized method of claim 9,wherein the rule data relating at least to the determined paging causecomprises rule data relating to a specific context of at least one ofthe computerized client device or a user of the computerized clientdevice within which the at least one of the computerized client deviceor the user currently operates.
 11. A computerized method of managingpaging notifications for a computerized user device, the computerizeduser device configured to transition wireless service from a firstwireless network to a second wireless network, the computerized methodcomprising: generating data relating to one or more rules relating toone or more user applications, the one or more user applicationsassociated with the computerized user device; and causing configurationof the computerized user device according to the generated data relatingto the one or more rules, the causing of the configuration comprisingcausing the computerized user device to be able to both (i) at leastevaluate one or more first paging notifications issued from the firstwireless network according to the one or more rules; and (ii) at leastevaluate one or more second paging notifications issued from the secondwireless network according to the one or more rules; wherein each of theone or more first paging notifications and each of the one or moresecond paging notifications is associated with at least one of the oneor more user applications.
 12. The computerized method of claim 11,wherein the first wireless network comprises a first public land mobilenetwork (PLMN) operated by a first network operator, and the secondwireless network comprises a second PLMN operated by a second networkoperator different from the first network operator.
 13. The computerizedmethod of claim 12, wherein: the first network operator comprises amobile network operator (MNO), and the second network operator comprisesa Multiple Systems Operator (MSO); and the transition of the wirelessservice from the first wireless network to the second wireless networkcomprises the computerized user device changing geographic location froma first coverage area associated with the first wireless network to asecond coverage area associated with the second wireless network. 14.The computerized method of claim 11, wherein the transition of thewireless service from the first wireless network to the second wirelessnetwork comprises the computerized user device changing geographiclocation from a first coverage area associated with the first wirelessnetwork to a second coverage area associated with the second wirelessnetwork; and wherein the computerized method further comprisesperforming: the (i) at least evaluation of the one or more first pagingnotifications issued from the first wireless network according to theone or more rules, when the computerized user device is located withinthe first coverage area; and the (ii) at least evaluation of the one ormore second paging notifications issued from the second wireless networkaccording to the one or more rules, when the computerized user device islocated within the second coverage area.
 15. The computerized method ofclaim 11, wherein: the first wireless network comprises a cellularwireless infrastructure utilizing licensed radio frequency (RF)spectrum; and the second wireless network comprises a small-cell basednetwork utilizing quasi-licensed RF spectrum.
 16. The computerizedmethod of claim 15, wherein: the computerized user device comprises afixed wireless device having dual-SIM (subscriber identity module)capability; at least one coverage area of the first wireless network hasoverlap with at least one coverage area of the second wireless network;and the fixed wireless device is located within the overlap.
 17. Thecomputerized method of claim 11, wherein at least one of the firstwireless network and the second wireless network comprises a small-cellbased network utilizing RF (radio frequency) spectrum within a 3GPP(Third Generation Partnership Project) 5G NR-U (New Radio-Unlicensed)mmWave band.
 18. The computerized method of claim 11, wherein thecomputerized method further comprises at least evaluating the one ormore first paging notifications issued from the first wireless networkaccording to the one or more rules, the evaluating occurring at least inpart while a fixed wireless device is actively communicating data withthe second wireless network, the evaluating comprising determiningwhether the computerized user device should either: (a) at leasttemporarily ignore the one or more first paging notifications; or (b)establish active communication with the first wireless network tofurther process the one or more first paging notifications.
 19. Computerreadable apparatus comprising a storage medium having at least onecomputer program stored thereon, the at least one computer programconfigured to, when executed on a wireless-enabled computerized device,cause the wireless-enabled computerized device to: receive user inputsregarding at least one paging notification rule; cause transmission offirst data relating to the received user inputs to a network entity, thetransmission of the first data enabling the network entity to causeconfiguration of at least some paging notifications for thewireless-enabled computerized device according to the at least onepaging notification rule, the configuration of the at least some pagingnotifications comprising inclusion of respective ones of second datawithin each of the at least some paging notifications; receive at leastportions of the configured at least some paging notifications, thereceived at least portions enabling the at least one computer program todetermine the respective ones of the second data; and based at least inpart on the determined respective ones of the second data, selectivelycause processing of at least some of the configured at least some pagingnotifications.
 20. The computer readable apparatus of claim 19, wherein:the user inputs comprises an input relating to a designation to beapplied to one or more user application computer programs operative toexecute on the wireless-enabled computerized device; the second datacomprises paging cause data, respective ones of the paging cause databeing different for different ones of the at least some pagingnotifications; and the selective causation of the processing of theconfigured at least some paging notifications comprises evaluation of aplurality of PDU (protocol data unit) session options for subsequentprocessing of IP (Internet Protocol) packet data associated withrespective ones of the one or more user application computer programs.